home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20021006-20030409
/
000078_JDanSkinner@JDanSkinner.com_Thu Nov 14 11:33:24 EST 2002.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
3KB
|
81 lines
Article: 13844 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!bloom-beacon.mit.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: JDanSkinner@JDanSkinner.com (Dan Skinner)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kermit FTP script
Date: 13 Nov 2002 21:07:55 -0800
Organization: http://groups.google.com/
Lines: 62
Message-ID: <8ce22d01.0211132107.1a569739@posting.google.com>
References: <8ce22d01.0211131301.2d2c8112@posting.google.com> <aqufg7$39f$1@newsmaster.cc.columbia.edu>
NNTP-Posting-Host: 24.159.192.106
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1037250475 20876 127.0.0.1 (14 Nov 2002 05:07:55 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 14 Nov 2002 05:07:55 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13844
Thanks guys;
I knew I was missing something.
I only went as far as the basic FTP scripting examples.
Now I can fix it right.
Do you think success is the right answer to a failed login?
The rules are the rules, but sometimes logic should prevail.
Anywho - I appreciate the quick and clear help.
When this script is done it will be run by cron as part of a scheduled
backup on the network. I'll find out what happened by email so (as
you say) if fail is a big deal and the more info in the email the
better. I'm using Kermit FTP rather than native FTP for this reason.
I have several other systems using this cron strategy with native FTP
This is the first new server on the network since version 8. I
suppose a rational person would go back and fix the old ones? But then
would a rational guy be watching Letterman and talking to you all?
Regards...Dan.
>jaltman@watsun.cc.columbia.edu (Jeffrey Altman) wrote in message news:<aqufg7>$39f$1@newsmaster.cc.columbia.edu>...
> FTP OPEN will not result in FAILURE because of a failed login
> attempt. The OPEN succeeds if you are connected to the FTP
> server.
>
> If you want to automate the login and be able to test the result:
>
> SET FTP AUTOLOGIN OFF
> FTP OPEN hostname
> IF FAILURE ...
> FTP USER username password
> IF FAILURE ...
>
>
>
> In article <8ce22d01.0211131301.2d2c8112@posting.google.com>,
> Dan Skinner <JDanSkinner@JDanSkinner.com> wrote:
> : ; FTP script from Linux archive to skinner /icsdemo
> : set command quoting on
> : set login prompt
> : set network tcp/ip
> : if fail end 1 TCP/IP Failed
> : set input echo on
> : ftp open skinner /user:root /password:xxxxxx
> : if fail exit 1 connection failed
> : ftp cd /icsdemo
> : ftp put jdsmenuarch.tar
> : ftp put gbsarch.tar
> : quit
> :
> : The script above works when the ftp open is correct.
> : if also works correctly (fails) if the ftp server does not exist.
> : It is broken if the server exists but the login fails.
> : IE: the put commands are issued.
> : I've made it as simple as I can but can't see what I'm doing wrong.
> : Using Linux 8.0.206 on Mandrake distro.
> : Skinner is SCO OpenServer 5.04 if that matters?
> :
> : Any help appreciated.
> : Regards...Dan.
>
>
> Jeffrey Altman * Sr.Software Designer Kermit 95 2.0 GUI available now!!!
> The Kermit Project @ Columbia University SSH, Secure Telnet, Secure FTP, HTTP
> http://www.kermit-project.org/ Secured with MIT Kerberos, SRP, and
> kermit-support@columbia.edu OpenSSL.